[CI] Ensure spec processing works even if path contains a space #5422
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
chalin
force-pushed
the
chalin-im-cp-pages-relative-paths-2024-10-16
branch
from
675563a to
38ecdbd
Compare
svrnm
approved these changes
Oct 18, 2024
24 tasks
olamideTiana
pushed a commit
to olamideTiana/opentelemetry.io
that referenced
this pull request
Oct 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
cp-pages.shscript, and make the (very reasonable assuption) that the script is being run from the repo root. I can't recall why I opted for absolute path names. None of the directory names inside of the repo contain any spaces, so we're good.@FatumaA, can you confirm (once this lands)?